Allow to use --write-sql to save the migration execution log to file #979
Conversation
|
The fact you didn't touch |
|
I think that is more a travis issue rather than php |
goetas
force-pushed
the
write-path
branch
2 times, most recently
from
9ea43ec to
a051421
Compare
|
I noticed that the phpunit output was very slow, and also, XDebug seems to be disabled in a non standard way: Line 15 in 9bd1bc3 |
|
Link to the standard way: https://docs.travis-ci.com/user/languages/php/#disabling-preinstalled-php-extensions |
|
Anyway I think you are right, because there definitely was output before it displayed "No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself." |
|
Found the issue. It was waiting for user input (when running migrations it ask to confirm before proceeding). It seems that recent symfony console detects that the terminal is not interactive. I have updated the test. |
|
Ah nice! That was tricky! |
Summary
In the 2.x version, passing
--write-sqlimplied--dry-run.This PR decouples the two, so is possible to run:
--dry-runwithout writing the result to file--dry-runand--write-sql--write-sqlto have a "log" of executed queries